Skip to content

Conversation

@PavelPashov
Copy link
Contributor

@PavelPashov PavelPashov commented Nov 12, 2025

This PR aims to resolve race conditions when a (p)subscribe is issued during connect status. Currently it's possible to either send a client or info handshake command after the (p)subscribe command has been issued and this might result either in the client rejecting the non-subscriber related command or the server rejecting it depending on the timing when the subscriber command was issued. This fix might lead to a situation in which some of the handshake commands are not sent to the server, however for example the ready check, which sends the info command does not make sense to happen on a subscriber connection, since the connection can only issue subscriber mode commands to the server.

Fixes #2037

@PavelPashov PavelPashov force-pushed the fix/pubsub-on-connect-issues branch from 0869378 to 2ed91b2 Compare November 12, 2025 07:30
@PavelPashov PavelPashov force-pushed the fix/pubsub-on-connect-issues branch 2 times, most recently from eda55a0 to 9dc4f39 Compare November 12, 2025 11:25
@PavelPashov PavelPashov force-pushed the fix/pubsub-on-connect-issues branch from 9dc4f39 to f1012bd Compare November 12, 2025 11:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

info command issued after client enters subscriber mode

1 participant